# Account Linking

## ♻️ Current situation & Problem
In the `FirebaseEmailPasswordAccountService` of our project, the
`signUp` function solely handles the creation of new user accounts or
signing in with OAuth credentials. This process did not account for
users who are already signed in (possibly anonymously) and wish to link
their accounts with email and password credentials. See
[#54](StanfordBDHG/PediatricAppleWatchStudy#54)
for details.


## ⚙️ Release Notes 
- The `signUp` function in `FirebaseEmailPasswordAccountService` now
supports linking new email and password credentials to already signed-in
users (including anonymous accounts).
- If onboarding starts with an anonymous account, users can expect a
seamless transition when upgrading from said anonymous account to a
permanent one.
- Fixes an issue where the reauthentication alert doesn't work.


## 📚 Documentation
The modification ensures that if a user is already signed in
(anonymously or with OAuth credentials), their account can be upgraded
with email and password credentials by linking these new credentials to
their existing account. See [Firebase
documentation](https://firebase.google.com/docs/auth/ios/anonymous-auth)
for details.


## ✅ Testing
TBD.


## 📝 Code of Conduct & Contributing Guidelines 

By submitting creating this pull request, you agree to follow our [Code
of
Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md)
and [Contributing
Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md):
- [x] I agree to follow the [Code of
Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md)
and [Contributing
Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md).

---------

Co-authored-by: Andreas Bauer <[email protected]>

# Study Enrollment via Invitation Code Authentication and Customize
Onboarding

## ♻️ Current situation & Problem
Currently, there is no way to validate the identity of the user of the
app to enroll them in the study.


## ⚙️ Release Notes 
- Customized Spezi Onboarding Flow to have language and symbols relevant
to Engage
- Integrated invitation code authorization into the onboarding flow,
using cloud functions to validate supplied code against a database of
valid codes stored in Firebase.


## 📚 Documentation
Integrated code based on:
StanfordBDHG/PediatricAppleWatchStudy#54.

The Onboarding flow now has custom views:

<img width="256" alt="Screenshot 2024-04-09 at 10 24 14 PM"
src="https://github.com/StanfordBDHG/ENGAGE-HF/assets/108841122/ee4b1fe0-d560-4918-8de0-28be1d7aa7b3">
<img width="256" alt="Screenshot 2024-04-09 at 10 26 21 PM"
src="https://github.com/StanfordBDHG/ENGAGE-HF/assets/108841122/a06f18b1-a944-4008-968b-0eab1aa36ca0">
<img width="256" alt="Screenshot 2024-04-09 at 10 26 28 PM"
src="https://github.com/StanfordBDHG/ENGAGE-HF/assets/108841122/57d05f25-86d5-409c-8d92-31f25c7a17ed">

See SpeziOnboarding for documentation of the other views.

## ✅ Testing
Thoroughly tested the onboarding flow, including the invitation code
authorization and account creation process.


### Code of Conduct & Contributing Guidelines 

By submitting creating this pull request, you agree to follow our [Code
of
Conduct](https://github.com/StanfordBDHG/.github/blob/main/CODE_OF_CONDUCT.md)
and [Contributing
Guidelines](https://github.com/StanfordBDHG/.github/blob/main/CONTRIBUTING.md):
- [X] I agree to follow the [Code of
Conduct](https://github.com/StanfordBDHG/.github/blob/main/CODE_OF_CONDUCT.md)
and [Contributing
Guidelines](https://github.com/StanfordBDHG/.github/blob/main/CONTRIBUTING.md).

---------

Co-authored-by: Paul Schmiedmayer <[email protected]>